Skip to content

chore: add initial Copilot instructions file TDE-1663#1279

Open
paulfouquet wants to merge 1 commit intomasterfrom
chore/add-copilote-instructions-tde-1663
Open

chore: add initial Copilot instructions file TDE-1663#1279
paulfouquet wants to merge 1 commit intomasterfrom
chore/add-copilote-instructions-tde-1663

Conversation

@paulfouquet
Copy link
Contributor

Motivation

Improving productivity using AI by giving more detailed and project-specific instructions to Copilot. The goal is to minimise the refinement the developer has to do with Copilot to get generated code or answers to questions.

Modifications

  • Add an initial instruction file for Copilot

Verification

#1277 & #1278

@paulfouquet paulfouquet requested review from a team as code owners October 15, 2025 22:49
@paulfouquet paulfouquet self-assigned this Oct 15, 2025

## Copilot Usage

- When asking Copilot for code, specify:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An example could be good here.

- Example commit: `fix(tileindex-validate): log source file on geo transform error`
- Example branch: `fix/log-tiff-source-on-geo-transform-error-tde-1677`

## Copilot Usage
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file is for copilot, not for us devs, so shouldn't contain instructions for us how to use copilot?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was thinking that an example would be good but as you say maybe this section shouldn't be here at all.

## Testing

- Use the `node:test` framework and `assert` for assertions.
- When generating tests, add them to the existing test file for the relevant module.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, we may need to be more succinct for this to be an effective prompt?

Suggested change
- When generating tests, add them to the existing test file for the relevant module.
- One test file for each module.

(Is module the correct term here?)

- Use the `node:test` framework and `assert` for assertions.
- When generating tests, add them to the existing test file for the relevant module.
- Use a new describe block if the function being tested does not already have one.
- Follow existing conventions for test names, structure, and assertions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we instead ask to align with existing conventions and harmonize/implement best practice where existing code deviates?

@@ -0,0 +1,45 @@
# GitHub Copilot Project Instructions

This file provides guidelines and instructions for using GitHub Copilot in this project. Amend and maintain this file as needed to help Copilot generate code and documentation that matches this project's standards and requirements.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this from a sample file? Might need to be removed

Copy link
Contributor

@schmidtnz schmidtnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General comment; I'm happy for this to be a rough first version and get refined regularly, as people use copilot more and identify what works and what doesn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants